Skip to main content

PR Workflow Summary

Here’s a quick summary of the PR workflow and how the staging issue was resolved. I initially installed nvm and upgraded the Node version to 24, but during the Azure build process we noticed that Azure currently supports only up to Node 22.20.0, so I rolled it back to that version. After that, I added the necessary environment variables to the GitHub workflow to make sure the CI/CD pipeline had everything it needed for deployment.

While testing in the staging environment, we ran into a “process is not defined” error. Cursor's Answer to why this happened: This happened because Vite’s dev server automatically includes a temporary compatibility layer for process, but in the production build that layer doesn’t exist. One of the dependencies — the Azure Storage SDK — references process at runtime, causing the error in the browser. To fix this, it added a Vite stub define: { 'process.env': {} } that provides an empty process.env object, ensuring the SDK’s runtime check passes without pulling in unnecessary polyfills or exposing any real environment variables.

The updated build has now been published with the Azure datasets, and everything is working as expected.